Method for identifying a mbsfn subframe at a user equipment (ue) in a wireless communication system

ABSTRACT

A method for identifying a MBSFN (Multimedia Broadcast multicast service Single Frequency Network) subframe at a user equipment (UE) in a wireless communication system is disclosed. Receiving module may receive receiving a subframe type information from an base station (BS). Receiving module may receive type information of the MBSFN subframe. The identifying module may identify an index of a MBSFN subframe based on the received subframe type information. The identifying module may identify a type of the MBSFN subframe based on the received type information of the MBSFN subframe. Decoding module may decode only a physical control channel region of the MBSFN subframe based on the identified type of the MBSFN subframe. Alternatively, Decoding module may decode the MBSFN subframe if the identified type of the MBSFN subframe is a decodable type or a known type.

TECHNICAL FIELD

The present invention relates to wireless communication, more specially,the present invention relates to method for identifying a MBSFN subframeat a user equipment (UE) in a wireless communication system.

BACKGROUND ART

In 3GPP (3rd Generation Partnership Project) specification, there aretwo basic subframe types. One type is unicast subframe and the othertype is MBSFN (Multimedia Broadcast multicast service Single FrequencyNetwork) subframe.

Unicast subframe is used for data and control channel transmission tospecific UE so that one-to-one communication may be performed betweeneNB and UE.

In contrary, the MBSFN subframe is used for broadcasting signals whichincludes data and control channel to targeted multiple receivers (e.g.,UE).

In the MBSFN subframe, a Release-8 UE does not know about the MBSFNsubframe structure except the first control channel part (length isindicated by PCFICH (Physical control format indicator channel)). Thus,the method for identifying a MBSFN subframe at the Release-8 UE isrequired.

Meanwhile, MBMS feature is introduced into Release-9 specification,Release-9 UE need to decode the MBSFN subframe. However, since thefeature of MBMS is just one of the targeting subframe types, this MBSFNsubframe is not defined as single subframe type. For example, as withduel cell/dual stream beamforming, a Release-9 UE may operate indifferent operation mode with legacy UE while achieving betterthroughput via MBSFN configuration.

In addition, LTE-A system (Release-10 or later system) may employvarious new feature considering higher order MIMO, CoMP (CoordinatedMulti-Point), Relay, and so on. Thus, additional new subframe types arerequired.

However, method for indicating MBSFN subframe and MBSFN subframe type torelease-8 UE, release-9 UE, and LTE-A UE are not studied yet.

DISCLOSURE OF INVENTION Technical Problem

Accordingly, the present invention is directed to a method foridentifying a MBSFN (Multimedia Broadcast multicast service SingleFrequency Network) subframe at a user equipment (UE) in a wirelesscommunication system that substantially obviates one or more problemsdue to limitations and disadvantages of the related art.

Solution to Problem

To achieve these objects and other advantages and in accordance with thepurpose of the invention, as embodied and broadly described herein, amethod for identifying a MBSFN (Multimedia Broadcast multicast serviceSingle Frequency Network) subframe at a user equipment (UE) in awireless communication system, the method includes receiving a subframetype information from an base station (BS); and identifying an index ofa MBSFN subframe based on the received subframe type information.

Also, the method may further include receiving type information of theMBSFN subframe; and identifying a type of the MBSFN subframe based onthe received type information of the MBSFN subframe.

In this case, the method may further include decoding the MBSFN subframeif the identified type of the MBSFN subframe is a decodable type or aknown type. Alternatively, the method may further include decoding onlya physical control channel region of the MBSFN subframe, or at least oneOFDM (Orthogonal frequency-division multiplexing) symbol excluding atraffic part of the identified MBSFN subframe if the identified type ofthe MBSFN subframe is a undecodable type or a unknown type.

In another aspect of the present invention, a user equipment (UE) forreceiving a signal in a wireless communication system, the UE includes areceiving module for receiving a subframe type information from an basestation (BS); and an identifying module for identifying an index of aMBSFN subframe based on the received subframe type information.

Also, the UE further includes a receiving module for receiving typeinformation of the MBSFN subframe; and an identifying module foridentifying a type of the MBSFN subframe based on the received typeinformation of the MBSFN subframe.

In this case, the UE may further include a decoding module for decodingthe MBSFN subframe if the identified type of the MB SFN subframe type isa decodable type or a known type. Alternatively, the UE may furtherinclude a decoding module for decoding only a physical control channelregion of the MBSFN subframe, or at least one OFDM (Orthogonalfrequency-division multiplexing) symbol excluding a traffic part of theidentified MBSFN subframe if the identified type of the MBSFN subframeis a undecodable type or a unknown type.

The UE may further include a decoding module for decoding only aphysical control channel region of the MBSFN subframe based on theidentified type of the MBSFN subframe.

Preferably, the the subframe type information is received via a RRC(Radio Resource Control) signaling.

Preferably, the type information of the MBSFN subframe information isreceived via a specific region of a downlink control channel, or apredefined control channel for MBMS (Multimedia Broadcast multicastservice) transmission.

Advantageous Effects of Invention

According to various embodiments of the present invention,

Release-8 UE, Release-9 UE, and LTE-A UE can efficiently decoding MBSFNsubframe. Thus, performance and throughput of the UE can be improved.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 is an example procedure for identifying received subframe type ata Release?8 UE;

FIG. 2 is an example procedure for identifying received subframe type ata Release-9 UE or later UE;

FIG. 3 is an example of subframe types according to specificationversion;

FIG. 4 shows an example of control channel forms which may be defined inthe future 3GPP releases for control channel extensions; and

FIG. 5 is a diagram for configuration of a user equipment apparatusaccording to one preferred embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details. For example, thefollowing description will be given centering upon a mobilecommunication system serving as an IEEE 802.16 system, but the presentinvention is not limited thereto and the remaining parts of the presentinvention other than unique characteristics of the IEEE 802.16 systemare applicable to other mobile communication systems.

In some cases, in order to prevent ambiguity of the concepts of thepresent invention, conventional devices or apparatuses well known tothose skilled in the art will be omitted and be denoted in the form of ablock diagram on the basis of the important functions of the presentinvention. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

In the following description, a user equipment (UE) may include mobileor fixed advanced mobile stations (AMSs), for example, a mobile station(MS) and the like. Also, the base station (BS) may refer to an arbitrarynode of a network end which communicates with the above terminal, andmay include a Node B (Node-B), an eNode B (eNode-B), eNB, and an accesspoint (AP) and the like.

In a mobile communication system, the UE may receive information fromthe Node B via a downlink, and may transmit information via an uplink.The information that is transmitted and received to and from the UEincludes data and a variety of control information. There are a varietyof physical channels according to categories of transmission (Tx) andreception (Rx) information of the UE.

The present invention discloses various methods for identifying MBSFNsubframe and MBSFN subframe type (MBSFN subframe configurationinformation) at a user equipment (e.g., release-8 UE, release-9 UE,LTE-A UE, and so on) according to the UE-type or class.

There are several classes which interpret the MBSFN subframes asdifferent subframe. The different interpretation may be true MBMSsubframe, relay backhaul subframe, LTE-A subframe, Release-9 subframe,and so on. Due to different subframe types with the same MBSFN(Multimedia Broadcast multicast service Single Frequency Network)signaling, the method and procedure to identify MBSFN subframe and MBSFNsubframe type at a user equipment (UE) is required.

MBSFN subframe configuration is defined as bitmap for the unicastsubframe which may be defined as MBSFN subframe by RRC (Radio ResourceControl) signaling.

The operation of Release-8 UE is simplified by a simple indication thatRRC configuration includes which subframes are MBSFN subframes and whichsubframes are not in the form of bitmap except for the special subframessuch as 0, 4, 5, 9 (FDD) subframe index of every radio frame.

In the contrary, for example, when an eNB tries to set subframe withindex 1 (zero-based index) to MBSFN subframe, the only required settingfor the Release-8 UE is the toggling of corresponding bit value to one.

The Release-8 UE may not listen from the corresponding MBSFN subframeany decodable or readable signal part except the unicast control regionwhich is defined with PCFICH (Physical Control Format Indicator Channel)value. Therefore, the eNB may easily differentiate the subframe type forthe Release-8 UEs.

FIG. 1 is an example procedure for identifying received subframe type ata Release?8 UE.

Referring to FIG. 1, the Release-8 UE may receive system informationwhich defines subframe types from an eNB S110. That is, the systeminformation may include indication which subframe is MBSFN subframe. TheRelease-8 UE may identify the subframe indices which are defined asMBSFN subframe using the received system information S120. Then, theRelease-8 UE may decode and listen only physical control channel part ofthe MBSFN subframes S130. The system information may be transmitted viaRRC (Radio Resource Control) signaling from an eNB

However, in case of Release-9 UE or later UE, the UE may decode andlisten to the MBSFN subframe if the corresponding subframe is decodableto itself.

For example, true MBMS (Multi Broadcasting Multicast Service) messagemay exist within the MB SFN subframe and a UE may try to decode thesignal traffic to receive MBMS contents. Since Release-9 UE or later UEmay want to listen to MBSFN subframe, it is preferable to providemeasures including any advanced feature in later releases specification.In addition to MBMS broadcast, there is dual-cell/dual stream operationwhich is defined as subframe specific operation.

Therefore, the total MBSFN type required for Release-9 or later UE maybe at least 2 types (MBMS, dual cell/dual stream, etc) or at least 3types (MBMS, dual cell/dual stream, relay backhaul, CoMP, etc).

It is noted that the total number of MBSFN subframe types and thesubframe type definitions may be different depending on the systemspecification (LTE Release 8, LTE Release- 9, LTE-A, etc).

FIG. 2 is an example procedure for identifying received subframe type ata Release-9 UE or later UE.

Referring to FIG. 2, the Release-9 UE or later UE may receive systeminformation which defines subframe types from an eNB S210. That is, thesystem information may include indication which subframe is MBSFNsubframe. Then, the Release-9 UE or later UE may identify MBSFN subframeand/or MBSFN subframe type which are known to itself such as MBMS, dualcell/dual stream, CoMP, relay, etc S220. Additional information abouttype of MBSFN subframe may be obtained from system information orcontrol channel. The Release-9 UE or later UE may listen and decode tocorresponding MBSFN subframes if the identified MBSFN subframe type isthe decodable or known subframe types for the Release-9 UE or later UES230.

Otherwise, the Release-9 UE or later UE may listen and decode to onlyphysical control channel part of the corresponding MBSFN subframe if theidentified MBSFN subframe type is not known or undecodable to theRelease-9 UE or later UE S230.

Release-10 UE or later (e.g., LTE-A) UE may listen and decode theRelease-9 subframes and newly defined subframes which will be includedin the future releases. LTE-A UE also may behave the same way asprevious Release-8 UE or Release-9 UE about the identification of MBSFNsubframe, since the corresponding message is already defined in thesystem message.

In case of LTE-A system, there are several extended MBSFN subframe typessuch as relay backhaul subframe, CoMP subframe, or LTE-A high order MIMOoperation subframe, etc. Among the extended MBSFN subframe types, relaybackhaul subframe is used to communicate between an eNB and an UE.

Relay backhaul subframe is a blank subframe so that relay may transmitonly unicast control channel part. A rest part excluding the unicastcontrol channel part in relay backhaul subframe is left emptyintentionally. Therefore, LTE-A UE may not listen and decode to theMBSFN subframe except for the control channel part.

If high order MIMO feature is employed and MBSFN subframe type isutilized for the definition, then additional CSI-RS (measurement RS) maybe defined in this MBSFN subframe, where the CSI-RS (Channel StateInformation Reference Signal) may be located in the unicast controlchannel region, PDSCH (Physical Downlink Shared CHannel) region, orLTE-A only FDM segment which will be newly defined.

In this MBSFN subframe type, LTE-A UE may listen to the subframe, decodeunicast traffic and measure the channel response whose result will bereported to the serving eNB or collaborating eNBs.

On the other hand, if CoMP scheme is employed into MBSFN subframe due tointersubcarrier interference or timing mismatch or collaborating cell'smeasurement purpose, then LTE-A UE may measure and report severalmeasurement results on channel quality, timing alignment information,spatial information related with MIMO operations, and so on. Inaddition, LTE-A UE may receive its own traffic from multipletransmission points.

The LTE-A UE may listen to system information including informationabout the MBSFN configuration. The information about the MBSFNconfiguration indicates which subframe is MBSFN subframe. In this case,the MBSFN configuration information may be defined as Release-8 system.

The LTE-A UE may listen to system information or control channels whichincludes the additional information about the MBSFN subframe types whichmay be applied to MBSFN configured subframes.

The LTE-A UE may also listen to the system information or controlchannels which includes additional information on the newly definedMBSFN subframe types which is not defined in Release-9 but LTE-A system.

For decodable/readable MBSFN subframe, LTE-A UE need to listen to thecorresponding subframes and do properly decoding and measurements. Fornon-decodable/unknown subframes, LTE-A UE need to read only the readablepart such as control channel part or the minimum number of OFDM symbolswhich is not defined as MBSFN traffic part.

FIG. 3 is an example of subframe types according to specificationversion.

Referring to FIG. 3, one radio frame may include 10 subframes. The oneradio subframe may include unicast subframe type and MBSFN subframetype. In this case, the MBSFN subframe type may be divided into at leastone type (e.g., MBSFN type 0, 1, 2, 3, 4 and 5).

As shown in FIG. 3, a Release 8-UE may view unicast subframes. However,the Release 8-UE does not know information about MBSFN subframe. Thus,the Release 8-UE receives system information including informationindicating MBSFN subframe type. Then, the Release 8-UE may identify theindex of the MBSFN subframe and decode only physical control channel ofthe identified MBSFN subframe.

As shown in FIG. 3, a Release 9-UE may view unicast subframes and MBSFNsubframes (e.g., MBMS subframe type and dual cell/dual stream subframetype).

The Release-9 UE receives system information including informationindicating MBSFN subframe type. Then, the Release 9-UE identifies theindex of the MBSFN subframe. Then, the Release-9 UE identify MBSFNsubframe type which is known to itself such as MBMS, dual cell/dualstream, CoMP, relay, etc. Additional information about type of MBSFNsubframe may be obtained from system information or control channel. TheRelease-9 UE listen and decode to corresponding MBSFN subframes if theidentified MBSFN subframe type is the decodable or known subframe typesfor the Release-9 UE.

Otherwise, the Release-9 UE listen and decode to only physical controlchannel part of the corresponding MBSFN subframe if the identified MBSFNsubframe type is not known or undecodable to the Release-9 UE.

LTE Release-8 specification defines the MBSFN subframe as bitmapsequence which corresponds to unicast subframes in a radio frame, thetotal number of bits may be 24 (6*4) bits for 40 ms period. This isaligned with HARQ process period (8 ms) and radio frame period (10 ms).

Therefore, if the MBSFN subframe type information is semi-staticinformation for system operation, the information for indicatingsubframe type may be located into system information such as RRCmessage. However, if the subframe type may be dynamically used by eNBand UEs, then the subframe type need to be reconfigured on-demand andindicated on dynamic channel.

The dynamic channel may be allocated to common search region which isPDCCH (Physical Downlink Control Channel) region existing in everysubframe or UE-specific search region which is private PDCCH region.However, arbitrary UE ID may be indicated as for the control informationindication.

For indicating MBSFN subframe types, new control channel which mayreside in the PDSCH or Frequency Division Multiplexed subcarriers whichis located out-side of legacy subframe region during the same subframetime duration.

When the dynamic MBSFN subframe type indication is adopted, the controlchannel may be transmitted at the same MBSFN subframe or transmitted atprior to the corresponding MBSFN subframe so that the UE may have enoughtime to detect the subframe type of following subframes.

The possible indication combination may be as follows. For indicatingRelease-8 MBSFN subframe, MBSFN subframe indication is transmitted viasystem information (e.g., RRC).

For indicating Release-9 MBSFN subframe, indication of MBSFN subframetype is transmitted via system information (RRC), or Common searchregion in PDCCH, or newly defined control channel for MBMS in PDSCH orPDCCH.

As shown in FIG. 3, a Release-10 UE may view unicast subframe type,MBSFN subframe type (e.g., MBMS, relay, CoMP, dual cell/dual stream).

FIG. 4 shows an example of control channel forms which may be defined inthe future 3GPP releases for control channel extensions.

For indicating Release-10 MBSFN subframe type or later (LTE-A) MBSFNsubframe type, information about MBSFN subframe type indication istransmitted via system information (e.g., RRC), or Common search region405 in PDCCH 415, or UE-specific search region 410 in PDCCH 415, ornewly defined control channel 425, 430 for MBMS in PDSCH 420 or PDCCH415, or new LTE-A control channel 425, 430, 445, or 450 which is locatedin PDSCH 420 or Frequency Division Multiplexed sub-carriers which isdisjointed with LTE UEs (e.g., the subcarriers in the LTE-A segment 435,440 which does not share with LTE-UE but exists in the same subframetime duration).

As known in FIG. 4, FIG. 4 show several control forms which can bedefined in the future 3GPP releases for control channel extensions. Acontrol channel for the most straightforward design may be located incommon-search region 405 and UE-specific region 410. However, due toblind decoding complexity and robustness issue, new control channel 425,430 may be located in the shared channel region 420 in a manner of TDM(Time Division Multiplexing), FDM (Frequency Division Multiplexing), orhybrid of the TDM and the FDM, etc.

In this case, if the corresponding subframe is MBSFN subframe, the newlydesigned subframe may be considered as MBMS channel. If thecorresponding subframe is interpreted as feature enhanced subframe, thenthe control channel may be Release-9 or LTE-A specific control channelfor common information sharing or UE-specific control information.

On the other hand, if the load of LTE UEs becomes small compared toLTE-A traffic, then the legacy system bandwidth may occupy less than thecarrier bandwidth. In this case, the remained subcarrier region may bedefined as LTE-A only segment or LTE-A only zone, control channel may bedefined in a manner of TDM, FDM, or hybrid of the TDM and the FDM.

In this case, several control channels may be defined in the newlydefined LTE-A only zone 435, 440 which may include the subframe typeindication, control channel shape indication, UE grant information,common control information, inter-cell co-operation information,reference symbol definition, and so on.

It is noted that the type definition of MBSFN may be applied toextension component carrier, which may be introduced into LTE-A or laterreleases. That is, the subframe type on extension component carrier maybe defined as special subframes so that behavior of UE may be controlledon the basis of subframes. In this case, by defining accesspriority/class for each subframe type, system may be easily enhancedover new LTE-A releases. In such case, the interpretation behaviordisclosed above may be applied similarly.

As described above, according to the present invention, the MBSFNsubframe indication is facilitated without UE ambiguity on the futurereleases. In addition, the proposed methods will promote the MBSFNsubframe usage to enhance system throughput and inter-cell operations.

FIG. 5 is a diagram for configuration of a user equipment apparatusaccording to one preferred embodiment of the present invention.

Referring to FIG. 5, the UE may include a receiving module 510,processor 520, a transmitting module 530, and memory 540.

The receiving module 510 may receive a subframe type information from anbase station (BS). The receiving module 510 may receive type informationof the MBSFN subframe.

Processor 520 may include a identifying module 521 and a decoding module522.

The identifying module 521 may identify an index of a MBSFN subframebased on the received subframe type information. The identifying module521 may identify a type of the MBSFN subframe based on the received typeinformation of the MBSFN subframe.

The decoding module 522 may decode only a physical control channelregion of the MBSFN subframe based on the identified type of the MBSFNsubframe.

The decoding module 522 may decode the MBSFN subframe if the identifiedtype of MBSFN subframe is a decodable type or a known type.Alternatively, the decoding module 522 may decode only a physicalcontrol channel region of the MBSFN subframe or at least one OFDM(Orthogonal frequency-division multiplexing) symbol excluding a trafficpart of the identified MBSFN subframe if the identified type of theMBSFN subframe type is a undecodable type or a unknown type.

The receiving module 510 and the transmitting module 530 are coupled tothe processor 520 and receive and/or transmit radio signals.

The memory 540 may information calculated in the processor 520 for apredetermined period of time, and may be replaced with a buffer (notshown) or the like.

The embodiments described below are provided by combining components andfeatures of the present invention in specific forms. The components orfeatures of the present invention can be considered optional if notexplicitly stated otherwise. The components or features may beimplemented without being combined with other components or features.The embodiments of the present invention may also be provided bycombining some of the components and/or features. The order ofoperations in the embodiments of the present invention may be changed.Some components or features of one embodiment may be included in anotherembodiment or may be replaced with corresponding components or featuresof another embodiment.

The embodiments of the present invention may be implemented by variousmeans, for example, hardware, firmware, software, or a combinationthereof.

In a hardware configuration, methods according to the embodiments of thepresent invention may be implemented by one or more application specificintegrated circuits (ASICs), digital signal processors (DSPs), digitalsignal processing devices (DSPDs), programmable logic devices (PLDs),field programmable gate arrays (FPGAs), processors, controllers,microcontrollers, microprocessors, etc.

In a firmware or software configuration, methods according to theembodiments of the present invention may be implemented in the form ofmodules, procedures, functions, etc. which perform the above-describedfunctions or operations. Software code may be stored in a memory unit soas to be driven by a processor. The memory unit is located at theinterior or exterior of the processor and may transmit data to andreceive data from the processor via various known means.

The detailed description of the exemplary embodiments of the presentinvention has been given to enable those skilled in the art to implementand practice the invention. Although the invention has been describedwith reference to the exemplary embodiments, those skilled in the artwill appreciate that various modifications and variations can be made inthe present invention without departing from the spirit or scope of theinvention described in the appended claims. For example, those skilledin the art may use each construction described in the above embodimentsin combination with each other.

Accordingly, the invention should not be limited to the specificembodiments described herein, but should be accorded the broadest scopeconsistent with the principles and novel features disclosed herein.

INDUSTRIAL APPLICABILITY

A method for identifying a MBSFN (Multimedia Broadcast multicast serviceSingle Frequency Network) subframe at a user equipment (UE) in awireless communication system is applicable to IEEE 802.16m, 3GPP LTEsystem, and like that.

1. A method for identifying a MBSFN (Multimedia Broadcast multicastservice Single Frequency Network) subframe at a user equipment (UE) in awireless communication system, the method comprising: receiving asubframe type information from an base station (BS); and identifying anindex of a MBSFN subframe based on the received subframe typeinformation.
 2. The method of claim 1, further comprising: receivingtype information of the MBSFN subframe; and identifying a type of theMBSFN subframe based on the received type information of the MBSFNsubframe.
 3. The method of claim 2, further comprising decoding only aphysical control channel region of the MBSFN subframe based on theidentified type of the MBSFN subframe.
 4. The method of claim 2, furthercomprising decoding the MBSFN subframe if the identified type of theMBSFN subframe is a decodable type or a known type.
 5. The method ofclaim 2, further comprising decoding only a physical control channelregion of the MBSFN subframe, or at least one OFDM (Orthogonalfrequency-division multiplexing) symbol excluding a traffic part of theidentified MBSFN subframe if the identified type of the MBSFN subframeis a undecodable type or a unknown type.
 6. The method of claim 1,wherein the subframe type information is received via a RRC (RadioResource Control) signaling.
 7. The method of claim 1, the typeinformation of the MBSFN subframe is received via a specific region of adownlink control channel, or a predefined control channel for MBMS(Multimedia Broadcast multicast service) transmission.
 8. The method ofclaim 7, wherein the downlink control channel is a PDCCH (PhysicalDownlink Control CHannel), and the specific region of the downlinkcontrol channel is a common search region or a UE-specific search regionof the PDCCH.
 9. A user equipment (UE) for identifying a MBSFN(Multimedia Broadcast multicast service Single Frequency Network)subframe at a user equipment (UE) in a wireless communication system,the UE comprising: a receiving module for receiving a subframe typeinformation from an base station (BS); and an identifying module foridentifying an index of a MBSFN subframe based on the received subframetype information.
 10. The UE of claim 9, further comprising: a receivingmodule for receiving type information of the MBSFN subframe; and anidentifying module for identifying a type of the MBSFN subframe based onthe received type information of the MBSFN subframe.
 11. The UE of claim9, further comprising a decoding module for decoding only a physicalcontrol channel region of the MBSFN subframe based on the identifiedtype of the MBSFN subframe.
 12. The UE of claim 10, further comprising adecoding module for decoding the MBSFN subframe if the identified typeof MBSFN subframe is a decodable type or a known type.
 13. The UE ofclaim 10, further comprising a decoding module for decoding only aphysical control channel region of the MBSFN subframe, or at least oneOFDM (Orthogonal frequency-division multiplexing) symbol excluding atraffic part of the identified MBSFN subframe if the identified type ofthe MBSFN subframe is a undecodable type or a unknown type.
 14. The UEof claim 9, wherein the subframe type information is received via a RRC(Radio Resource Control) signaling.
 15. The UE of claim 9, the typeinformation of the MBSFN subframe information is received via a specificregion of a downlink control channel, or a predefined control channelfor MBMS (Multimedia Broadcast multicast service) transmission.
 16. TheUE of claim 15, wherein the downlink control channel is a PDCCH(Physical Downlink Control CHannel), and the specific region of thedownlink control channel is a common search region or a UE-specificsearch region of the PDCCH.